-
Notifications
You must be signed in to change notification settings - Fork 828
add logical plan distributed optimizer to query frontend #6974
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
FragmentAddr string | ||
} | ||
|
||
func NewRemoteNode() Node { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This might need to take expr as a parameter
return []*Node{&r.Expr} | ||
} | ||
func (r *Remote) String() string { | ||
return fmt.Sprintf("%s%s", r.Op.String(), r.Expr.String()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to mention the node name remote
. Maybe similar to what Thanos has fmt.Sprintf(remote(%s), r.Expr.String())
d12b7f8
to
11e8995
Compare
11e8995
to
e7384c5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for addressing all of the comments!
Signed-off-by: rubywtl <[email protected]>
e7384c5
to
8d33af3
Compare
What this PR does:
Implements a distributed optimizer in the distributed execution middleware that introduces remote nodes in the logical plan to mark fragmentation points. It focuses on binary aggregation queries and includes un-marshal functionality to maintain remote node integrity in the processing pipeline
Which issue(s) this PR fixes:
For distributed query execution feature
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]